Skip to content

gitignore: ignore target as a symlink#133

Merged
bluss merged 1 commit into
bluss:masterfrom
mathstuf:target-as-symlink
Oct 4, 2019
Merged

gitignore: ignore target as a symlink#133
bluss merged 1 commit into
bluss:masterfrom
mathstuf:target-as-symlink

Conversation

@mathstuf

@mathstuf mathstuf commented Oct 1, 2019

Copy link
Copy Markdown
Contributor

No description provided.

@bluss

bluss commented Oct 4, 2019

Copy link
Copy Markdown
Owner

Curious where this use case comes from

@bluss bluss merged commit 8c3634a into bluss:master Oct 4, 2019
@tbu-

tbu- commented Oct 4, 2019

Copy link
Copy Markdown
Collaborator

If you want to move all cargo target dirs globally, just do

export CARGO_TARGET_DIR=/var/tmp/cargo

@mathstuf mathstuf deleted the target-as-symlink branch October 4, 2019 19:33
@mathstuf

mathstuf commented Oct 4, 2019

Copy link
Copy Markdown
Contributor Author

I keep my build trees on a separate partition and wrangled using symlinks.

If you want to move all cargo target dirs globally

AFAIK, this doesn't work because then all builds of Rust code on my machine is serialized on the lock in the one target directory (I already have issues with ALE competing with my :mak build commands in Vim as it is).

@bluss

bluss commented Oct 4, 2019

Copy link
Copy Markdown
Owner

I would half suggest that you should just use a personal excludes configuration in git for that. See core.excludesFile in git help config.

@mathstuf

mathstuf commented Oct 4, 2019

Copy link
Copy Markdown
Contributor Author

I'm aware of that; I use it for things like my Vim backup files and the like. But this is a file that "every" clone of this ends up having. It's basically a backport of the new behavior of cargo new: rust-lang/cargo#4944

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants